home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
lnxd3-79.zip
/
DIGEST3.796
< prev
next >
Wrap
Internet Message Format
|
1993-01-01
|
21KB
From Linux-Activists-Request@news-digests.mit.edu Tue Dec 15 00:27:43 1992
Return-Path: <Linux-Activists-Request@news-digests.mit.edu>
Received: from bloom-picayune (BLOOM-PICAYUNE.MIT.EDU) by montefiore.ulg.ac.be (4.1/SMI-4.1)
id AA06115; Tue, 15 Dec 92 00:27:27 +0100
Received: by bloom-picayune (5.57/25-eef)
id AA00157; Mon, 14 Dec 92 18:00:49 -0500
Message-Id: <9212142300.AA00157@bloom-picayune>
From: Digestifier <Linux-Activists-Request@news-digests.mit.edu>
To: Linux-Activists@news-digests.mit.edu
Reply-To: Linux-Activists@news-digests.mit.edu
Date: Mon, 14 Dec 92 18:00:26 EST
Subject: Linux-Activists Digest #796
Status: R
Linux-Activists Digest #796, Volume #3 Mon, 14 Dec 92 18:00:26 EST
Contents:
[comp.os.linux.announce] Guidelines for posting (Matt Welsh)
Western Digital WD-8003Es; Do they work with linux? (Johann Miranda)
How to use this Enet card... (Ketil M. Malde)
0.99 general protection error (Corey Minyard)
Re: Problem with xv + X386 mono (Stew Ellis)
Re: ps that uses /proc (Lars Aronsson)
Epoch-4.2 binary uploaded (Thomas Dunbar)
Re: PC port I/O for Linux MS-DOS emulator (long) (Mike Arena)
Re: ext fs question (.badblocks) (David Fenyes,Neurobiol/Anatomy,5705,7901935)
Re: Pros/cons of linux/386bsd? (Rick Miller)
libX11.so.2.1 -- where? (Damien P. Neil)
----------------------------------------------------------------------------
Crossposted-To: comp.os.linux.announce,news.answers
From: mdw@db.TC.Cornell.EDU (Matt Welsh)
Subject: [comp.os.linux.announce] Guidelines for posting
Date: Mon, 14 Dec 1992 20:24:27 GMT
Archive-name: linux-faq/announce/guide
Last-modified: 6 Dec 1992
HOW TO POST TO COMP.OS.LINUX.ANNOUNCE
This article gives info on how and what to post to comp.os.linux.announce.
Please read the whole thing, to avoid any confusion. :)
To submit an article to this group, please mail the article to:
linux-announce@tc.cornell.edu
If you have questions or problems with posting to comp.os.linux.announce,
please send mail to the moderators at:
linux-announce-request@tc.cornell.edu
Or, you may send mail to us directly. The moderators for this group are
Matt Welsh (mdw@tc.cornell.edu) and Lars Wirzenius (wirzeniu@cc.helsinki.fi).
Whereas most versions of the C-News news software will automatically mail
postings to the moderator address, it may take some time for this address
to propagate (and there are many systems out there not supporting this
automatic mailing feature). Therefore, to ensure that your posting will get
to us, you should probably mail it to us by hand. Once we receive your article
and approve it, we will post your article.
NOTE: Your article will not show up in any newsgroups that it may be
crossposted to (e.g. other than comp.os.linux.announce) until we approve the
article. The delay should be negligible (we read email all the time), so
please don't post the same article seperately to other groups. That
causes multiple copies to be sent around under most setups.
Also, PLEASE crosspost your announcements to both comp.os.linux and
comp.os.linux.announce! Not everyone will be able to read the announce
newsgroup (e.g. FidoNet folks), and the point of this group is not to split
the bandwidth, but to provide a moderated portion of it in another group.
Remember: no announcement is too insignificant for this group. Don't be
afraid to submit something if you think it isn't important enough; that's
why we have moderators, to screen the content of the group. I plan to
approve almost anything (announcement-wise) that's submitted.
The following guidelines should be used when submitting articles:
- I will approve a wide range of articles for this group. The only postings
that are discouraged are discussions and questions about Linux.
This group is mainly for:
* Announcements of new software that has been ported to Linux
(e.g. "DikuMUD v4.2 is now available on sunsite....")
* Announcements of new versions or patchlevels of existing software,
such as GCC, the kernel, libraries, new versions of utilities and so on.
(e.g. "Linux v1.0 is finally available...")
* Bug fixes and software patches (or announcements of available patches).
If you have a fix for a known bug in any Linux software, please post
the fix and the relevant patch (if any). If the patch is huge, instead
post an announcement as to where it's available.
(e.g. "Patch to fix broken 0.98.5 scsi.c....")
* Summaries of responses for individual requests for information. If you
requested some Linux-related information on c.o.l, and are posting a
summary of that information, please submit it to c.o.l.a.
(e.g. "Summary: What's the best VGA card for Xfree86?")
* Just about anything else of any importance. If you're not sure if you
should post the article to c.o.l.a, submit it anyway. It can't hurt,
and most of the time your article will be approved anyway.
- When submitting articles, please include valid Newsgroups, Subject,
Keywords, From, and Date lines in the header. These may either be in
the mail header itself, or you may simply include the article, header
and all, in the body of the mail message. Please don't send mail with
only the body of the article to be posted, as this doesn't include
the Newsgroups: line and other article-specific information.
- When submitting articles, please use a descriptive Subject line.
If you crosspost the article to other groups, starting your subject with
"ANNOUNCEMENT" helps it to stick out in those groups. If you're posting a
patch or summary, use "SUMMARY" or "PATCH" at the beginning of your
subject, as "ANNOUNCEMENT" isn't quite appropriate.
- Also, please use a Keywords line in your header, so that articles may
be searched more easily in the archives (when we have the archives up).
The Keywords field should contain one or more of the following:
Type of announcement: new version, patch, urgent, summary, etc.
Package: kernel, GCC, X, TeX, SLS, jump tables, etc.
Type of program: A keyword or two on what your program is.
This is especially important if the program isn't part of
a well-known package. Ex: editor, tcpip utils, game, etc.
Version: 0.98.5, jumptables 4.2, etc.
For example, if you're announcing v4.2 of Shoopsort for Linux, you
might want a subject and keywords that look like this:
Subject: ANNOUNCEMENT: Shoopsoft v4.2 now ported to Linux
Keywords: Shoopsort 4.2, sorting algorithm, new port
Or, if you're announcing a summary on ethernet cards for Linux, you
could have:
Subject: SUMMARY: Best ethernet cards for Linux TCP/IP
Keywords: summary, ethernet, tcpip, cards, hardware
If you have any problems or questions, please contact the moderators at
linux-announce-request@tc.cornell.edu.
Thanks,
Matt Welsh mdw@tc.cornell.edu
Comp.os.linux.announce moderator
--
Matt Welsh mdw@tc.cornell.edu Cornell Theory Center
"Go on, emote! I was raised on thought balloons!"
------------------------------
From: miranda@frenzy.eng.uiowa.edu (Johann Miranda)
Subject: Western Digital WD-8003Es; Do they work with linux?
Date: 14 Dec 92 19:26:52 GMT
Hello, everybody. Yep, I am another happy linuxer :D>
While we are on the subject, does anyone know whether the WD8003Es ethernet card
works with linux? I know this is dangerously close to an FAQ, but hey! have you
read the whole thing recently? It's loooooooooooooooooooooooooong, man.
You can flame me or inform me by e-mail. If you would like to
know about this (see, there's this guy in the net that's selling the things
for like $55) also e-mail me. Thanks for your support.
By the way, I want to acknowledge my gratitude and admiration to
all of you that have ever contributed to linux and its growth. You are too
numerous to mention, but believe me, if I knew you all I could take a shot at
it. I don't want to leave anyone out,though. Thanks, Thanks,Thanks, Thanks,and
oh, yeah, keep up the good work! (Linus you reading this? way to go man!).
Adios. -JEM-
------------------------------
From: ketil@ii.uib.no (Ketil M. Malde)
Crossposted-To: comp.sys.ibm.pc.hardware,comp.dcom.lans.ethernet
Subject: How to use this Enet card...
Date: 14 Dec 92 21:24:26 GMT
Reply-To: ketil@ii.uib.no,magnus@ii.uib.no
Hello!
We are trying to interface a Linux system with the rest of the world
by using this ethernet card that we don't have any documentation for.
We are interested in *any* info you could have on this, including the
name of the manufacturer, but also things like device drivers to use,
etc etc.
THe card is an 8-bit ISA card, it has a chip labeled 'Reliability //
2VP1209 LAN-PAC(tm) // made in ireland' and a 40mHz crystal. There's
another important-looking (:-) chip labeled AM7990DC on it.
The sockets on the edge are one 9-pin D type plug, and one coax e-net
plug.
The date '16 FEB 1989' stamped in black, and the words 'ENET 1.4 LS'
are printed on the back side.
Any help deeply appreciated!
--
= Ketil Malde In real life: ketil@ii.uib.no =
= Nuke the whales! Honk if you love unicorns! =
------------------------------
From: minyard@crchh7b9 (Corey Minyard)
Subject: 0.99 general protection error
Date: Mon, 14 Dec 1992 18:42:08 GMT
The default 0.99 kernel gave me a general protection at startup. The kernel
was crashing in wake_up(). After some creative debugging (I added a stack
trace-back to the exception handler) I found the bug was coming from iput().
It turns out that the inode_wait variable was not being initialized to NULL.
Make the following change the following in fs/inode.c to fix the problem.
This is not really a diff, but you should get the idea:
***
static struct inode inode_table[NR_INODE];
static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait;
void inode_init(void)
{
***
static struct inode inode_table[NR_INODE];
static struct inode * last_inode = inode_table;
! static struct wait_queue * inode_wait = NULL;
void inode_init(void)
***
Corey
minyard@bnr.ca
------------------------------
From: ellis@nova.gmi.edu (Stew Ellis)
Subject: Re: Problem with xv + X386 mono
Date: 14 Dec 92 19:35:06 GMT
ghod@drycas.club.cc.cmu.edu writes:
>I was going to ask about this in a previous post, but it slipped my mind:
>I downloaded the binary for xv version 2.21 for use under SLS 98pl5. The
>program runs, but it fails to display images correctly. It seems as though the
>image is divided into vertical columns and the columns are out of order.
>The only images I've tried loading so far are GIFs and they all come out the
>same way. I do believe this to be a problem with the way it displays images,
>not in the way it reads them, for the following reason: when xv is invoked
>without any arguments, it displays an image of what seems to be an XV logo,
>and this image is distorted as well.
>I'm trying to run it under X386 1.1 (from SLS 98pl5) using the *MONOCHROME*
>server. My system is a 386SX (16Mhz) with 4 meg RAM. X seems to work fine
>otherwise. Does anyone have any idea what's wrong with xv? I have the compiler
>installed, so if it's just a matter of re-compiling, someone please let
>me know.
>-Bill Paul
>Assistant System Administrator
>New Windsor Associates L.P.
>ghod@drycas.club.cc.cmu.edu -or- ghod@drycas.bitnet
This seems to be a general bug in the Xfree86 mono server. I am running
Xfree-mono on SVR4 and have the same problem. I believe I have seen a
message from Dawes or Wexelblat acknowledging the problem.
--
-- ___________________
R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765 / _____ ______
Humanities & Social Science, GMI Eng.& Mgmt. Inst. / / / / / /
Flint, MI 48504 ellis@nova.gmi.edu /________/ / / / /
------------------------------
From: aronsson@lysator.liu.se (Lars Aronsson)
Subject: Re: ps that uses /proc
Date: 14 Dec 92 21:30:32 GMT
barr@stein.u.washington.edu (David Barr) writes:
>Has anyone written a version of ps that uses the proc file system? I
David, first, this posting is not an attack on your fine program.
>are a few major disadvantages of my program. Because I wrote it in a
>hurry, the output is kind of non-standard and there are only 3 options
What I would like to know is whether the INPUT follows any standard.
The presented program relies on the present file tree structure under
/proc. Will this structure stay the same for ever? Is it mentioned in
POSIX? Will it look the same in other operating systems? Otherwise,
does POSIX mention any system call or ioctl(2) operation to retrieve
information necessary for ps(1)? Could we finally, in some way or
another, write a portable ps(1) program?
In my mind, guessing about the file tree structure under /proc is
almost as primitive (not more primitive) as guessing about the
contents of /dev/kmem.
> sprintf(filename, "/proc/%s/%s", ent->d_name, what);
> proc = opendir("/proc");
> sprintf(filename, "/proc/%s", ent->d_name);
If there is no standard, maybe we should write one and send a copy to
the POSIX guys at IEEE.
--
Lars Aronsson, Lysator, Linkoping University, Linkoping, Sweden
------------------------------
Crossposted-To: comp.os.linux.announce
From: tdunbar@vttcf.cc.vt.edu (Thomas Dunbar)
Subject: Epoch-4.2 binary uploaded
Date: Mon, 14 Dec 1992 20:13:57 GMT
this archive (/pub/linux/packages/TeX/epoch42.taz at tsx-11.mit.edu)
contains a epoch-4.2 binary and misc. support files.
the binary was compiled with gcc-2.2.2d7 and linked shared with 4.1 libs
(and 2.1 xlibs). i have not included any files that are also available with
emacs-18.59 (eg, lisp files).
essential files from R. Marlet's viewer package are included (the complete
package is avail at babar.inria.fr, dir pub/emacs. it also has lucid
support and lots more fonts); only the math-courier fonts are included.
if u want to change the default font size used for math-mode's wysiwyg
TeX support --the main reason i've included epoch in this package--, change
the default near the end of math-mode.el.
the viewer files unpack to subdir of /ext which should be on an ext fs.
i've included /root/dot.emacs, which is my default .emacs file for both
epoch and x11emacs.
to install:
1 unpack this archive from the / dir (note: /ext is expected to be
on an ext fs.
2 cp /root/dot.emacs to ~/.emacs
3 cd /usr/X386/lib/X11/fonts/misc;mkfontdir
so that the math-courier fonts are available
4 restart X, epoch /ext/viewer/doc/math-mode-help.tex
page down till u get to some funny symbols and press F8 to
toggle math-mode. M-x math-mode-help for more info on math-mode.
now, type (a%-x%)^2 to check out the viewer stuff
thomas (tdunbar@vttcf.cc.vt.edu)
--
Send submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu
------------------------------
From: arena@goethe.credtech.com (Mike Arena)
Subject: Re: PC port I/O for Linux MS-DOS emulator (long)
Date: 14 Dec 92 18:15:49 GMT
Reply-To: arena@credtech.com (Mike Arena)
In article <77873@hydra.gatech.EDU> gt8134b@prism.gatech.EDU (Howlin' Bob) writes:
>dear Those in the Know,
>
>A plea for help:
>
> I am currently modifying Linux's (pre-alpha) MS-DOS emulator to
>support simulated port I/O; that is, if a program does an in
>from I/O address 0x2f8, I'll hand it the next available character
>on com2.
...
> So I come to you, the public, in a plea for help. I desperately
>need information on the 8250 UARTs (the 16550's seem to be 8250's with
>one extra FIFO control register, correct?), the 8259 interrupt
>controller, and the keyboard controller (number?). If you can't give
>me information about the chips, at least point me to a useful reference.
>I know I should probably get the Intel spec. sheets, but something about
>programming PC's would be just as good.
...
>Howlin' Bob
>Georgia Institute of Technology, Atlanta Georgia, 30332
>uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt8134b
>Internet: gt8134b@prism.gatech.edu
Look in Jeff Duntemann's articles in Dr. Dobb's Journal for most of 1991.
I think the first issue was around March.
He describes, in much detail, about interrupt-driven communication using
UART's on the PC. His set of articles are much better than any book I've
found which claimed to be "the bible" on PC communications.
--
Michael James Arena Credit Technologies Inc.
arena@credtech.com 281 Winter Street, Suite #100
(617) 890-2000 x237 Waltham, MA 02154
------------------------------
From: dfenyes@thesis1.med.uth.tmc.edu (David Fenyes,Neurobiol/Anatomy,5705,7901935)
Subject: Re: ext fs question (.badblocks)
Date: 14 Dec 1992 19:38:45 GMT
In article <1992Dec14.163449.15147@aston.ac.uk> evansmp@uhura.aston.ac.uk (Mark Evans) writes:
>Remy CARD (card@masi.ibp.fr) wrote:
>: mkefs now uses a reserved inode (inode #2) to store the bad blocks.
>: This inode does not appear in the filesystem tree any more because it was
>: leading to problems (root could delete the .badblocks file or save it during
>: a backup).
Is there a way to easily read the bad blocks list to verify that all the
bad blocks have been identified? (or even to modify it after the fs has
been created?)
David.
--
David Fenyes dfenyes@thesis1.med.uth.tmc.edu
University of Texas Medical School Houston, Texas
------------------------------
From: rick@ee.ee.uwm.edu (Rick Miller)
Crossposted-To: comp.unix.bsd
Subject: Re: Pros/cons of linux/386bsd?
Date: 14 Dec 1992 20:26:46 GMT
mharm@pollux.usc.edu (Michael Harm) writes:
>Hi folks.
>We are trying to decide whether to go with linux or 386bsd for
>our 486 machines. Particular constraints are:
First off... Who's "we"? That might give us a clue. You see, if "we"
is a law-sensitive organization you may want to avoid 386BSD because it's
derived from the NET-2 tapes which AT&T now claims to have Copyrights on.
>We don't have a lot of disk space.
Linux uses shared libraries, 386BSD doesn't. This means that Linux will
take up a *lot* less disk-space than 386BSD will... especially if you intend
to have lots of little executables (such as the usual suite of UNIX-ish
commands: ls, more, cat, etc.).
>We need X11.
Both do this, don't they?
>We don't have a lot of memory per machine.
Linux will run with only 2 MegaBytes (though the install's a bit trickier).
>We don't have cd roms
Neither Linux nor 386BSD require you to have a cdrom.
You didn't mention what you want to *DO* with your machines... That's CRITICAL.
If you want to do networking, perhaps 386BSD is your answer. But if you want
to be POSIX-compliant, it's Linux.
Rick Miller <rick@ee.uwm.edu> | <rick@discus.mil.wi.us> Ricxjo Muelisto
Occupation: Husband, Father, WEPCo. WAN Mgr., Discus Sys0p, and Linux fan
------------------------------
From: dpn2@po.CWRU.Edu (Damien P. Neil)
Subject: libX11.so.2.1 -- where?
Date: Mon, 14 Dec 1992 20:29:35 GMT
I FTPd xconquer from sunsite and installed it, but when I try to run it it
complains about not being able to find libX11.so.2.1 and dies. I looked
around, and found a libX11.so.2.0 in my /lib directory, so I assume that all
I need to do is get an update and put it in there. However, I can't seem to
find _any_ version of this file in tsx-11 or sunsite. Could someone please
point me in the right direction?
Thanks!
Back to installing 0.99...I love Linux...a real OS at last!
=====
Damien Neil dpn2@po.cwru.edu "Until somebody debugs reality, the best
Case Western Reserve University I can do is a quick patch here and there."
CMPS/EEAP double majoring masochist - Erik Green
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: Linux-Activists-Request@NEWS-DIGESTS.MIT.EDU
You can send mail to the entire list (and comp.os.linux) via:
Internet: Linux-Activists@NEWS-DIGESTS.MIT.EDU
Linux may be obtained via one of these FTP sites:
nic.funet.fi pub/OS/Linux
tsx-11.mit.edu pub/linux
tupac-amaru.informatik.rwth-aachen.de pub/msdos/replace
The current version of Linux is 0.98pl6 released on December 2, 1992
End of Linux-Activists Digest
******************************